Skip to content

Update sbt-scalajs, scalajs-compiler, ... to 1.18.2#4706

Merged
rossabaker merged 1 commit intomainfrom
update/sbt-scalajs-1.18.2
Jan 24, 2025
Merged

Update sbt-scalajs, scalajs-compiler, ... to 1.18.2#4706
rossabaker merged 1 commit intomainfrom
update/sbt-scalajs-1.18.2

Conversation

@typelevel-steward
Copy link
Copy Markdown
Contributor

@typelevel-steward typelevel-steward bot commented Jan 23, 2025

About this PR

📦 Updates

from 1.18.1 to 1.18.2

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (1.18.1).
You might want to review and update them manually.

build.sbt
⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-js" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

@rossabaker
Copy link
Copy Markdown
Member

rossabaker commented Jan 23, 2025

Build failure on ubuntu-22.04, 2.13, graalvm@21, catsJVM, before it gets lost:

==> X cats.jvm.tests.FutureSuite.Future: coflatMap.coflatten throughMap  3.015s munit.FailException: Failing seed: GEIc-SiLsh9TtmKVi8p5QBl9HapPSj3VaWdT6yiKHEL=
You can reproduce this failure by adding the following override to your suite:

  override def scalaCheckInitialSeed = "GEIc-SiLsh9TtmKVi8p5QBl9HapPSj3VaWdT6yiKHEL="

Exception raised on property evaluation.
> ARG_0: Future(Failure(java.util.concurrent.ExecutionException: Boxed Exception))
> Exception: java.util.concurrent.TimeoutException: Future timed out after [3 seconds]
    at munit.ScalaCheckSuite.propToTry(ScalaCheckSuite.scala:98)
Caused by: java.util.concurrent.TimeoutException: Future timed out after [3 seconds]
    at scala.concurrent.impl.Promise$DefaultPromise.tryAwait0(Promise.scala:248)
    at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:261)
    at scala.concurrent.Await$.$anonfun$result$1(package.scala:201)
    at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:62)
    at scala.concurrent.Await$.result(package.scala:124)
    at cats.jvm.tests.FutureSuite.cats$jvm$tests$FutureSuite$$$anonfun$eqfa$1(FutureSuite.scala:45)

@satorg
Copy link
Copy Markdown
Contributor

satorg commented Jan 23, 2025

@rossabaker , yeah, I see that issue in CatsJVM from time to time.
Not so often as the issues in CatsNative, but it also occurs.
I wonder if 3 secs is a reasonable limit for the tests for Future.
I mean, it should be enough when the test runs in isolation, but taking into account that there are so many tests running at the same time, cannot it be a case that the JVM is just very busy?

@rossabaker rossabaker merged commit 6a9f1d9 into main Jan 24, 2025
@satorg satorg deleted the update/sbt-scalajs-1.18.2 branch March 17, 2025 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@satorg satorg satorg approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@rossabaker @satorg